Expand description
RAUI core types and components
The things that most users will be interested in here are the components. Those have more documentation on how to use widgets, components, etc. in your app.
Modules§
- Animation engine
- Application foundation used to drive the RAUI interface
- Interactivity traits
- Layout engine
- Widget messaging
- Widget property types
- Renderer traits
- Widget signals
- Widget state types
- Widget types and the core component collection
Macros§
- Macro for implementing
MessageData
. - Macro for implementing
PropsData
. - Helper to manually create a
WidgetComponent
struct from a function. - A helper for getting the named children out of a widget context
Structs§
- Represents a JSON number, whether integer or floating point.
- Prints log messages to terminal via println! macro.
Enums§
- An error that can occur while processing a
Prefab
- Represents any valid JSON value.
Traits§
- Common logging interface that custom log engines should follow to enable their reusability across different modules that will log messages to text output targets. Objects that implement this trait should be considered text output targets, for example text streams, terminal, network-based loggers, even application screen.
- The
Prefab
trait is implemented for types that are able to translate to and fromPrefabValue
’s
Type Aliases§
Attribute Macros§
- Allows you to execute re-usable logic after your component body
- An attribute macro that allows you to add hooks that will execute before your component body
Derive Macros§
- Derive macro for the [
MessageData
][raui_core::messenger::MessageData] trait - Derive macro for the [
PropsData
][raui_core::props::PropsData] trait